Removable and replaceable tap domain selection circuitry

ABSTRACT

Today many instances of IEEE 1149.1 Tap domains are included in integrated circuits (ICs). While all TAP domains may be serially connected on a scan path that is accessible external to the IC, it is generally preferred to have selectivity on which Tap domain or Tap domains are accessed. Therefore Tap domain selection circuitry may be included in ICs and placed in the scan path along with the Tap domains. Ideally, the Tap domain selection circuitry should only be present in the scan path when it is necessary to modify which Tap domains are selected in the scan path. The present disclosure describes a novel method and apparatus which allows the Tap domain selection circuitry to be removed from the scan path after it has been used to select Tap domains and to be replaced back into the scan path when it is necessary to select different Tap domains.

This application is a divisional of application Ser. No. 13/693,592,filed Dec. 4, 2012, currently pending;

Which was a divisional of application Ser. No. 13/427,255, filed Mar.22, 2012, now U.S. Pat. No. 8,347,157, granted Jan. 1, 2013;

Which was a divisional of application Ser. No. 13/157,955, filed Jun.10, 2011, now U.S. Pat. No. 8,171,361, granted May 1, 2012;

Which was a divisional of application Ser. No. 12/835,373, filed Jul.13, 2010, now U.S. Pat. No. 7,984,349, granted Jul. 19, 2011;

Which was a divisional of application Ser. No. 12/555,512, filed Sep. 8,2009, now U.S. Pat. No. 7,783,948, granted Aug. 24, 2010;

Which was a divisional of application Ser. No. 12/128,384, filed May 28,2008, now U.S. Pat. No. 7,607,058, granted Oct. 20, 2009;

Which was a divisional of application Ser. No. 11/626,011, filed Jan.23, 2007, now U.S. Pat. No. 7,395,467, granted Jul. 1, 2008;

Which was a divisional of application Ser. No. 10/983,256, filed Nov. 4,2004, now U.S. Pat. No. 7,200,783, granted Apr. 3, 2007;

which claims priority from Provisional Application 60/517,250, filedNov. 4, 2003.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to 1) application Ser. No. 08/918,872, filedAug. 26, 1999, now U.S. Pat. No. 6,073,254, “Selectively Accessing TestAccess Ports in a Multiple Test Access Port Environment”, which ishereby incorporated by reference, 2) application Ser. No. 09/458,313,filed Dec. 10, 1999, now U.S. Pat. No. 6,324,614, issued Nov. 27, 2001,TAP With Scannable Control Circuit For Selecting First Test DataRegister In TAP Or Second Test Data Register In TAP Linking Module ForScanning Data”, which is hereby incorporated by reference, 3)application Ser. No. 09/277,504, filed Mar. 26, 1999, now U.S. Pat. No.6,324,662, issued Nov. 27, 2001, “A TAP and Linking Module for ScanAccess of Multiple Cores with IEEE 1149.1 Test Access Ports”, which ishereby incorporated by reference, and 4) application Ser. No.60/207,691, filed May 26, 2000, now U.S. Pat. No. 7,058,862, issued Jun.6, 2006, “Selecting Different 1149.1 TAP Domains From Update-IR State”,which is hereby incorporated by reference. This application claimspriority under 35 USC 119(e)(1) of provisional patent application Ser.No. 60/517,250, filed Nov. 4, 2003.

BACKGROUND OF DISCLOSURE

Today's ICs may contain many embedded 1149.1 TAP domains. Some of theseTAP domains are associated with intellectual property (IP) core circuitswithin the IC, and serve as access interfaces to test, debug, emulation,and programming circuitry within the IP cores. Other TAP domains mayexist in the IC which are not associated with cores but rather tocircuitry in the IC external of the cores. Further, the IC itself willtypically contain a TAP domain dedicated for operating the boundary scanregister associated with the input and output terminals of the ICs,according to IEEE std 1149.1.

FIG. 1 illustrates an example architecture for selecting Tap domainswithin an IC 102. This architecture is described in detail in referencedU.S. Pat. No. 7,058,862. In the architecture, Tap domains 1-3 (TD1-TD3)are shown to exist between input linking circuitry 108 and outputlinking circuitry 110 of circuit block 106. While three Tap domainsTD1-TD3 are shown in this example, any number of Tap domains may existbetween the input and output linking circuitry. Each Tap domain TD1-TD3has a Test Data Input (TDI) 112 coupled to the input linking circuitry108, a Test Data Output (TDO) 114 coupled to the input linking circuitry108 and output linking circuitry 110, and a control interface 116consisting of Test Clock (TCK), Test Mode Select (TMS), and a Test Reset(TRST) signals coupled to the input linking circuitry. The input linkingcircuitry 108 is coupled to a TDI input 122 to the IC and to TCK, TMS,and TRST control inputs 124 to the IC. The input and output linkingcircuits 108 and 110 are described in detail in the above referenceapplication and serve basically as multiplexing circuits thatselectively link Tap domains together serially between the IC's TDI 122and TDO 120 leads. The input linking circuitry also couples the IC's TCKand TMS inputs to the selected Tap domains control inputs 116 so theycan receive control to operate when coupled to the IC's TDI 122 and TDO120 leads. To be compliant to the IEEE 1149.1 boundary scan standard,the data on the IC's TDI 122 lead is clocked into the architecture onthe rising edge of TCK 124 and the data on the IC's TDO 120 lead isclocked from the architecture on the falling edge of TCK 124. While notshown, circuitry is assumed to exist on the TDO 120 lead to allow datafrom the architecture to be clocked out on the falling edge of TCK.

The Tap Domain Selection (TDS) circuit 104 is coupled to the IC's TDOoutput via serial path 120, to the output linking circuitry 110 viaserial path 118, to the input and output linking circuits 108 and 110via control bus 126, and potentially to other circuits in the IC viacontrol bus 126. The TDS circuit is also coupled to the IC's TCK, TMS,and TRST input leads 124. In response to control bus 126 input from TDS104, the input and output linking circuitry may serially connect any oneor combination of Tap domains TD1-TD3 between the IC's TDI 122 andserial path 118 to the TDS for access. For example, Tap domainconnections may be made between the IC's TDI 122 and serial path 118that includes; TD1 only, TD2 only, TD3 only, TD1 and TD2, TD1 and TD3,TD1 and TD2 and TD3, or TD2 and TD3. As seen, the TDS circuit remains inthe scan path, along with the selected Tap domains, to complete theserial connection path between the IC's TDI 122 and TDO 120 leads. Inthe referenced U.S. Pat. No. 7,058,862, the TDS was referred to as a TapLinking Module (TLM). The TDS of this application is slightly differentfrom the TLM, and so it has been named differently. With the exceptionof TDS 104, the architecture of FIG. 1 is like that described in U.S.Pat. No. 7,058,862.

FIG. 2 illustrates a simple example of an IEEE 1149.1 Tap domainarchitecture 202. The Tap domain architecture includes a Tap controller204, an instruction register (IR) 206, at least one data register (DR)208, and multiplexer circuitry 210. Each of the Tap domains TD1-TD3 andthe TDS 104 are based on Tap domain architecture 202. The abovementioned difference between the TDS and TLM was that the TLM did notnecessarily require a DR in the Tap domain architecture, a directconnection between TDI and TDO could be used in place of a DR in theTLM. It should be understood however, that the TLM could be substitutedfor the TDS if desired to make to the two Tap domain architectures bethe same. In response to TCK and TMS control inputs to Tap controller204, the Tap controller outputs control to capture data into and shiftdata through either the IR 206 from TDI to TDO or a selected DR 208 fromTDI to TDO. The data shifted into IR 206 is updated and output on bus214, and the data shifted into a DR is updated and output on bus 212. DR208 may also capture data from bus 212 and IR 206 may capture data frombus 214. Buses 212 and 214 form bus 126 of TDS 104 in FIG. 1. Inresponse to a TRST input to the Tap controller 204, the TAP controller,IR and DR are reset to known states. The structure and operation of IEEE1149.1 Tap domain architectures like that of FIG. 2 are well known.

FIG. 3 illustrates in more detail the structure 302 of the IR 206 and DR204 of FIG. 2. As seen, the structure 302 includes a shift register 304coupled to TDI and TDO for shifting data, and an update register 306coupled to the parallel outputs of the shift register for updating datafrom the shift register. If FIG. 3 is seen to represent IR 206, theshift register 304 will shift data from TDI to TDO in response to theTap controller being in the Shift-IR state 1210 of FIG. 12. Followingthe shift operation, the Tap controller will output an UpdateIR signal308, in the Update-IR state 1212 of FIG. 12, to cause the updateregister 306 to parallel load the data shifted into the shift register.If FIG. 3 is seen to represent DR 208, the shift register 304 will shiftdata from TDI to TDO in response to the Tap controller being in theShift-DR state 1214 of FIG. 12. Following the shift operation, the Tapcontroller will output an UpdateDR signal 308, in the Update-DR state1216 of FIG. 12, to cause the update register 306 to parallel load thedata shifted into the shift register. If seen as a DR, bus outputs 310and 312 represent bus 212 of FIG. 2. If seen as an IR, bus outputs 310and 312 represent bus 214 of FIG. 2. Bus 310 is the normal update outputbus from the update register. Bus 312 is a bus output from the shiftregister. The use of bus 312 by the present disclosure will be describedlater in regard to FIG. 11.

FIG. 4 is provided to simply show that TDS 104 can be positioned beforeTap domain circuit block 106 if desired. The TDS still operates the sameto select Tap domains in circuit block 106, it is just repositioned inthe IC's TDI to TDO scan path.

FIG. 5 illustrates an example 502 where four ICs 102 are connectedtogether serially from TDI 504 to TDO 506 on a board or other substrate.This example illustrates use of referenced U.S. Pat. No. 7,058,862. EachIC 102 is also connected to TCK, TMS, and TRST 508 control inputs on theboard or other substrate. In this arrangement, each IC's internal Tapdomains in circuit block 106 can be selected, via each IC's TDS 104, tobe included in or excluded from the TDI 504 to TDO 506 scan path. Forclarification, one TAP domain 202 comprising an IR 206 and a DR 208 isshown being selected within each IC's TAP domain circuit block 106 ofarrangement 502. As seen, the TDS's of each IC 102 are always includedin the scan path from TDI 504 to TDO 506. Maintaining the TDS's in theTDI 504 and TDO 506 scan path after they have served their purpose ofselecting Tap domains hinders the optimization of serial test, debug,emulation, and/or programming operations. For example, during test,debug, emulation, and/or programming operations, 1149.1 instruction scanoperations to IRs 208 and data scan operations to DRs 208 may be usedintensely. Having to pad the instruction and data scan patterns with theadditional bits required to traverse the TDS's IR 206 and DR 208 scanpaths extends the scan pattern length beyond that of the selected Tapdomain's IR 206 and DR 208. Also it requires editing each individualinstruction and data scan pattern transmitted from TDI 504 to TDO 506 toinsert the padding bits for the TDS circuit's IR 206 and DR 208.

It is therefore desirous to provide a method of removing TDS circuitsfrom a TDI to TDO scan path after they have been used to select Tapdomains and to provide a method of replacing TDS circuits back into aTDI to TDO scan path when it is necessary to again access them to selecta new group of Tap domains for access in a TDI to TDO scan path. It isan object of the present disclosure that the removal of TDS circuitsfrom the TDI to TDO scan path be achieved using only the IC's IEEE1149.1 interface signal leads. It is also an object of the presentdisclosure that the replacement of TDS circuits back into the TDI to TDOscan chain be achieved using only the IC's IEEE 1149.1 interface signalsand without having to:

1. reset the Tap domain test logic in an IC by activating the TRST inputor by cycling the Tap controller of the Tap domains into the Test LogicReset state using the TMS input,2. cycle power to the ICs,3. in any way alter or lose any stored state information in the ICsfunctional and Tap domain test circuitry, or4. disturb the state of any legacy Tap domains of ICs in the scan paththat do not use the Tap domain selection architecture of FIG. 1 or 4.

FIELD OF THE DISCLOSURE

This disclosure relates in general to integrated circuit designs, and inparticular to improvements in the design of IEEE 1149.1 Tap domain basedtest, debug, emulation, and programming architectures included inintegrated circuits.

SUMMARY OF THE DISCLOSURE

The present disclosure provides a method of removing and replacing Tapdomain selecting (TDS) circuits in a TDI to TDO scan path. The TDSremoval and replacement processes are achieved using only the standard1149.1 interface leads of the IC. Importantly, the TDS replacementprocess is achieved without needing to; (1) reset the ICs test logic,(2) cycle power to the IC, (3) alter/lose any stored state informationin the ICs functional/test circuitry, or (4) disturb the state of legacyIC Tap domains.

DESCRIPTION OF THE VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of an IC that includes multiple Tapdomains and a Tap Domain Selection (TDS) circuit.

FIG. 2 illustrates an example of an IEEE 1149.1 Tap domain architecture.

FIG. 3 illustrates an example of the shift register and update registersections of an IEEE 1149.1 instruction or data register.

FIG. 4 illustrates an alternate placement of the TDS circuit of theexample in FIG. 1.

FIG. 5 illustrates a first scan path configuration whereby the ICs inthe scan path contain multiple Tap domains and a TDS circuit.

FIG. 6 illustrates a second scan path configuration whereby the ICs inthe scan path contain multiple Tap domains and a TDS circuit.

FIG. 7 illustrates a first scan path configuration that consists of ICscontaining Tap domains and a TDS circuit and a legacy IC that containsonly one Tap domain.

FIG. 8 illustrates a second scan path configuration that consists of ICscontaining Tap domains and a TDS circuit and a legacy IC that containsonly one Tap domain.

FIG. 9 illustrates an example IC that includes multiple Tap domains andcircuitry for removing and replacing the TDS circuit in the IC's scanpath according to the present disclosure.

FIG. 10 illustrates an example Tap controller design for use in TDScircuits to facilitate the removal and replacement of the TDS circuitaccording to the present disclosure.

FIG. 11 illustrates an example multiplexer control circuit forcontrolling the removal and replacement of TDS circuits according to thepresent disclosure.

FIG. 12 illustrates the state diagram of an IEEE standard 1149.1 Tapcontroller.

FIG. 13 illustrates a first timing example of a convention IEEE 1149.1state entry and exit.

FIG. 14 illustrates the modification of the first timing of FIG. 13 toallow inputting of the special protocol of the present disclosure forreplacing TDS circuits.

FIG. 15 illustrates a second timing example of a convention IEEE 1149.1state entry and exit.

FIG. 16 illustrates the modification of the second timing of FIG. 13 toallow inputting of the special protocol of the present disclosure forreplacing TDS circuits.

FIG. 17 illustrates an alternate placement of the TDS removal andreplacement circuitry of the example in FIG. 9.

FIG. 18 illustrates an IC including the TDS removal and replacementcircuit, multiple Tap domains, and a Tap Domain Bypass (TDB) circuitaccording to the present disclosure.

FIG. 19 illustrate and example circuit for implementing the TDB circuitof FIG. 18 according to the present disclosure.

FIG. 20 illustrates a first scan path configuration whereby the ICs inthe scan path contain multiple Tap domains, TDS removal and replacementcircuitry, and the TDB circuit according to the present disclosure.

FIG. 21 illustrates a second scan path configuration whereby the ICs inthe scan path contain multiple Tap domains, TDS removal and replacementcircuitry, and the TDB circuit according to the present disclosure.

FIG. 22 illustrates a first scan path configuration that consists of ICscontaining multiple Tap domains, TDS removal and replacement circuitry,and TDB circuits, and a legacy IC that contains only one Tap domainaccording to the present disclosure.

FIG. 23 illustrates a second scan path configuration that consists ofICs containing multiple Tap domains, TDS removal and replacementcircuitry, and TDB circuits, and a legacy IC that contains only one Tapdomain according to the present disclosure.

FIG. 24 illustrates an example IC that contains a single Tap domain, TDSremoval and replacement circuitry, and a TDB circuit according to thepresent disclosure.

DETAILED DESCRIPTION OF DISCLOSURE

FIG. 6 illustrates the example 502 of FIG. 5 whereby the TDS circuits104 have been removed from the TDI 504 and TDO 506 scan path accordingto the present disclosure. As seen, after the TDS circuits 104 areremoved, as indicated conceptually by the signal path passing throughdotted line circuit block 104, each IC's TDI to TDO scan path onlyincludes the selected Tap domain's IR 206 and DR 208 in the circuitblock 106. The IC's TDS circuit 104 therefore does not contribute IR andDR pad bit lengths to instruction and data scan operations occurring inthe selected Tap domains of the ICs. Replacing the TDS circuits backinto the scan path again enables access to the TDS circuit's IR 206 andDR 208 as shown in the example 502 of FIG. 5 to allow selectingdifferent Tap domains in the ICs. The replacement of TDS circuits backinto the scan path is advantageously achieved by the present disclosureusing only the IEEE 1149.1 IC test leads and without requiring any ofthe listed items 1-4 above.

FIG. 5 illustrates that each IC in the TDI to TDO scan path contains theTap domain selection architecture of FIG. 1. However, in practice,legacy or preexisting ICs may be used in the TDI to TDO scan path alongwith ICs that include the Tap domain selection architecture.

FIG. 7 illustrates an example scan path of ICs 702 that includes atleast one of the above mentioned legacy ICs 704 (C). The legacy IC 704(C) does not include the Tap domain selection architecture of the otherICs 102 (A,B,D) in the scan path. In this example, the legacy IC (C) isassumed to contain only one Tap domain 202 between its TDI and TDOleads. This one Tap domain may be the IC's 704 IEEE 1149.1 boundary scanTap domain. With the TDS circuits in the scan path, instruction scanoperations pass through the IRs 206 of the selected Tap domains and TDScircuits of ICs 102 (A,B,D), and through the IR 206 of IC 704 (C).Likewise, with the TDS circuits in the scan path, data scan operationspass through the DRs 208 of the selected Tap domains and TDS circuits ofICs 102 (A,B,D), and through the DR 208 of IC 704 (C).

FIG. 8 illustrates the scan path example 702 whereby the TDS circuits ofICs 102 (A,B,D) have been removed from the scan path as they were inFIG. 6, leaving only the IRs 206 and DRs 208 of the ICs (A,B,C,D)between TDI 708 and TDO 706. The process of removing the TDS circuits inICs (A,B,D) is achieved via the IEEE 1149.1 test bus and is transparentthe legacy IC (C). When it is necessary to select different Tap domainsin ICs (A,B,D), the TDS circuits are again inserted into the TDI 708 toTDO 706 scan path as seen in FIG. 7. According to the presentdisclosure, the process of replacing the TDS circuits back into the scanpath is achieved via the IEEE 1149.1 test bus and without requiring anyof the listed items 1-4 above, which includes not having to modify thestate of Tap domain(s) in legacy ICs (C).

FIG. 9 illustrates an IC 902 showing in detail the modifications to theTap domain selection architecture of FIG. 1 to achieve the TDS circuitremoval and replacement operations. As can be seen the modifications arecontained in circuit block 916 and include a multiplexer (M) circuit904, a multiplexer control (MC) circuit 906, and a modified TDS circuit920. The Tap domain circuit block 106 of IC 902 remains the same as inFIG. 1. TDS circuit 920 receives the serial output 118 from Tap domaincircuit block 106, control input from bus 124, and a control input frommultiplexer control circuit 906. TDS circuit 920 outputs a serial output918 to one input of multiplexer circuit 904, the control bus 126, and acontrol signal 908 to multiplexer control circuit 906. The other inputof multiplexer circuit 904 is connected to the serial output 118 fromTap domain circuit block 106. The output of multiplexer circuit 906 iscoupled to the TDO lead 912 of IC 902. The multiplexer control circuit906 receives an input 910 from the TDS control bus 126, inputs 908 fromthe Tap controller 204 within TDS circuit 920, and an input from theexternally accessible TMS lead on bus 124. The multiplexer controlcircuit 906 outputs a control signal 914 to multiplexer 904 and TDScircuit 920. The control signal 914 to multiplexer 904 is used to coupleone of the multiplexer circuits inputs to the IC's TDO lead. The controlsignal 914 to TDS circuit 920 is used to enable or disable the IR 206and DR 208 paths of TDS circuit 920.

Following a power up of IC 902 or upon the Tap controller 204 beingplaced in the Test Logic Reset state 1202 of the Tap state diagram inFIG. 12, signal 914 from the multiplexer control circuit 906 will be setto couple the serial output 918 of TDS circuit 920 to the IC's TDO lead912 such that instruction and data scan operations occurring in IC 902will include the TDS circuit's IR 206 and DR 208 paths. Also controlsignal 918 will be set to enable control bus 124 to control access tothe IR 206 and DR 208 paths of TDS circuit 920. In this condition, theTap domain selection architecture in IC 902 operates to select Tapdomains in circuit block 106 like the Tap domain architecture of IC 102of FIG. 1. When Tap domains have been selected and it is desired toremove the TDS circuit from the ICs TDI 122 to TDO 912 scan path, theTDS circuit 920 will output a signal 910 on control bus 126 to themultiplexer control circuit 906. In response to this signal, multiplexercontrol circuit 906 will output control on signal 914 that; (1) causesmultiplexer 904 to couple serial path 118 to the IC's TDO lead 912 whichremoves the TDS circuit 920 from the IC's TDI to TDO scan path, and (2)disables bus 124 from being able to control the TDS circuit's IR 206 andDR 208 scan paths. In this condition, the TDS circuit 920 is removedfrom the IC's TDI to TDO scan path and the present state of the TDScircuit's IR and DR paths is maintained until the TDS circuit 920 isreplaced back into the IC's TDI to TDO scan path.

When it is necessary to replace the TDS circuit 920 back into the IC'sTDI to TDO scan path to allow selecting a different one or more Tapdomains in circuit block 106, a special protocol is input on the IC'sTCK and TMS signal leads. This special protocol is designed to berecognized only by the multiplexer control circuit 906. The Tapcontrollers 204 of the selected Tap domains and TDS circuit 920 do notrecognize the input of the special protocol and simply ignore its input.When input, the special protocol causes the control output 914 frommultiplexer control circuit 906 to be set back into the state that; (1)couples the TDS circuit's serial output 918 to the IC's TDO lead 912 viamultiplexer 904, and (2) enables control bus 124 to again control the IR206 and DR 208 scan paths in TDS circuit 920. This special protocol isone of the key aspects of the present disclosure.

FIG. 10 illustrates the details of the TDS circuit 920. TDS circuit 920differs from the TDS circuit 104 which, as previously mentioned, appearsas a conventional Tap domain 202 shown in FIG. 2. A first difference isthat the TDS circuit 920 includes a blocking circuit 1002 which islocated between the Tap controller's output bus 1004 and the controlinput bus 1006 to the IR and DR scan paths. When the TDS circuit 920 isincluded in the IC's TDI to TDO scan path, the Remove Select signal 914from the multiplexer control circuit 906 will be set to allow signals topass through the blocking circuit 1002 from the Tap controller outputbus 1004 to the input bus 1006 to the IR and DR scan paths, enabling theTap controller to control the IR and DR scan paths during instructionand data scan operations. However, when the TDS circuit 920 is removedfrom the IC's TDI to TDO scan path, the Remove Select signal 914 will beset to disable signals from the Tap controller output bus 1004 frompassing through blocking circuit 1002 to be input to the IR and DR scanpaths via input bus 1006. When TDS circuit 920 is removed, the outputbus 1006 from blocking circuit 1002 will be set to states that preventoperation of the IR and DR scan paths. Thus when the TDS circuit 920 isremoved from the IC's scan path, the values stored in the TDS circuit'sIR and DR scan paths do not change during subsequent instruction anddata register scan operations that occur in the IC's TDI to TDO scanpath. The only signal from the Tap controller output bus 1004 that isnot blocked from being input to the IR and DR input bus 1006 is the Tapcontroller's Reset signal. The Tap controller's Reset signal is assertedlow whenever the Tap controller 204 enters the Test Logic Reset state1202 to initialize/reset the IR, DR, and other circuitry that needs tobe initialized. The Tap controller's Reset signal passes through theblocking circuit 1002 independent of the state of the Remove Selectsignal 918. This insures that the IR and DR scan paths of the TDScircuit 920 can be initialized to known states whenever the Tapcontroller 204 enters the Test Logic Reset state 1202 of the Tap statediagram of FIG. 12.

A second difference is that the TDS circuit 920 includes a Tapcontroller 204 output bus 908 which is input to the multiplexer controlcircuit 906. As will be described in more detail later in regard to FIG.11, the Tap controller output bus 908 provides control signals and Tapstate information to allow the multiplexer control circuit 906 toperform its functions of; (1) removing the TDS circuit 920 from the IC'sTDI to TDO scan path, and (2) replacing the TDS circuit 920 back intothe IC's TDI to TDO scan path. It is important to note that the Tapcontroller 204 of TDS circuit 920 continues to follow the IEEE 1149.1protocol on the TCK and TMS inputs of bus 124, independent of the valueof the Remove Select signal 914. Thus Tap control output bus 908 isalways in lock step with the IEEE 1149.1 TCK and TMS protocol. Thisallows the Tap controller 204 of a removed TDS circuit 920 to remainprotocol synchronous with the selected Tap domains in circuit block 106.Maintaining protocol synchronization between a removed TDS circuit andthe selected Tap domains in circuit block 106 ensures that the Tapcontrollers of selected Tap domains and TDS circuit are moving throughthe same Tap controller states together. This is important since thespecial protocol used to replace a TDS circuit back into an IC's TDI toTDO scan path should only be issued during selected Tap controllerstates that are assumed to be in common with and synchronized to boththe TDS's Tap controller and the Tap domain's Tap controller. In thisspecification, the selected states for enabling the special protocol tobe issued include the RunTest/Idle state 1204, Shift-IR state 1210,Shift-DR state 1214, Pause-IR state 1208, and Pause-DR state 1206 of theTap state diagram in FIG. 12.

FIG. 11 illustrates in detail the multiplexer control circuit 906, whichfunctions to control the removal and replacement operations of the TDScircuit 920 in the IC's 902 TDI to TDO scan path. The multiplexercontrol circuit 906 contains three DFFs 1102-1106, and two And gates1108-1110.

The data input of DFF 1102 is coupled to Remove signal 910 from TDScircuit 920 output bus 126. The rising edge triggered clock input of DFF1102 is coupled to either the UpdateIR or UpdateDR control signal fromTap controller output bus 908, depending upon which TDS 920 scan pathregister (IR or DR) is used to provide the Remove signal 910. The dataoutput of DFF 1102 is coupled to the Remove Select signal 914 which, aspreviously described, is input to multiplexer 914 and TDS circuit 920.The reset input of DFF 1102 is coupled to the output of And gate 1110.One input of And gate 1110 is coupled to the Reset signal from the TDS920 circuit's Tap controller 204 on bus 908. The other input of And gate1110 is coupled to the data output of DFF 1106.

The data input of DFF 1104 is coupled to a logic low value. The dataoutput of DFF 1104 is coupled to the data input of DFF 1106. The dataoutput of DFF 1106 is coupled to And gate 1110 and is referred to as theReplace signal. The rising edge triggered clock input of DFF 1104 iscoupled to the TMS signal from bus 124. The falling edge triggered clockinput of DFF 1106 is also coupled to the TMS signal from bus 124. BothDFFs 1104 and 1106 have a low active Set input that is coupled to theoutput of And gate 1108. One input of And gate 1108 is coupled to theReset input from bus 908 and the other input of And gate 1108 is coupledto a Replace State signal from bus 908. The Replace State signal is asignal that indicates the Tap controller 204 of TDS 920 is in anappropriate state for the special protocol to be issued for replacing aremoved TDS 920 back into the ICs TDI to TDO scan path. In the examplesillustrated in this specification for the purpose of describing thedisclosure, the appropriate states for producing the Replace Statesignal are selected to be the RunTest/Idle state 1204, Shift-DR state1214, Shift-IR state 1210, Pause-DR state 1206, and Pause-IR state 1208of the Tap state diagram of FIG. 12.

When the Tap controller of TDS 920 is in one of these states, theReplace State signal will be set high. During all other Tap states theReplace State signal is set low. One example circuit for producing theReplace State signal on bus 908 when the Tap controller of TDS 920 is inone of the above mentioned states is illustrated as Or gate 1218 of FIG.12. In this example, the Or gate 1218 would be included in the Tapcontroller of TDS 920 to output the Replace State signal on bus 908.Alternately, Or gate 1218 could be included external of the TDS 920 Tapcontroller or in the multiplexer control circuit 906 if desired.Including it in the TDS 920 Tap controller allows outputting one signal(Replace State) from the Tap controller on bus 908 to multiplexercontrol circuit 906 as opposed to having to output five signals(RunTest/Idle, Shift-DR, Shift-IR, Pause-DR, Pause-IR) from the Tapcontroller on bus 908 if included in the multiplexer control circuit 906or external of the Tap controller. While these Tap controller stateshave been seen most appropriate to be selected and used by the presentdisclosure, different, more, or less Tap controller states could beselected as well by design choice.

When the Tap domain selection architecture of IC 902 is reset at powerup or by moving the Tap controllers 204 to their Test Logic Reset state1202 by asserting a low on TRST 124 or by applying five logic ones onTMS 124, the Reset signal on bus 908 from the TDS 920 Tap controller 204is set low. The low on the Reset signal clears DFF 1102 to a logic zerooutput on Remove Select signal 914 and sets DFFs 1104 and 1106 to outputlogic ones (the Replace signal to And gate 1110 is set high). While theTap controller 204 of TDS 920 is in the Test Logic Reset state 1202, theReplace State signal will be low since the Tap controller is not in anyof the selected Tap states. The low on the Replace State signal willmaintain DFFs 1104 and 1106 in a set state (Replace is high) when theTap controller 204 of TDS 920 exits the Test Logic Reset state andenters any of Tap states other than RunTest/Idle, Shift-DR, Shift-IR,Pause-DR, or Pause-IR.

With the TDS circuit 920, multiplexer control circuit 906, andmultiplexer 904 of circuit block 916 initialized as described above, theTDI to TDO scan path of IC 902 includes the TDS circuit in with thecurrently selected Tap domain(s) in circuit block 106. Thus the ICs scanpath appears as shown and described in regard to FIGS. 5 and 7, with theexception that circuit blocks 916 replace the TDS circuits 104 in theFigures. In this configuration, the TDS circuits 920 of circuit blocks916 may operate to select different Tap domains to be included in orexcluded from the IC's scan path. When it is desired to remove the TDScircuits from the IC's scan path, the Remove signal input to multiplexercontrol circuit 906 on bus 910 from TDS 920 is set high.

As mentioned in regard to FIG. 3, the IR 206 and DR 208 of TDS 104 andTDS 920 may include both a bus output 310 from the Update Register 306and a bus output 312 from the Shift Register 304. Both of these busesform the output bus 212 of the DR and the output bus 214 of the IR.Buses 212 and 214 in turn form the output bus 126. The Remove signal 910from TDS 920 is a signal from bus 126 and can come from either bus 310or 312 of IR bus 212 or DR bus 214. Preferably, but not necessarily, theRemove signal 910 will come from bus 312 of the IR or bus 312 of the DR.The advantage in doing this is that the Remove signal is made availableat the input of DFF 1102 so that the UpdateIR control signal (if fromthe IR) or the UpdateDR control signal (if from the DR) can clock theRemove signal into DFF 1102 at the same time as the control signals(UpdateIR or UpdateDR) clock data from the Shift Register 304 into theUpdate Register 306. This method allows the DFF 1102 to appear as anadditional Update Register bit of either the IR or DR scan path.

For example, and assuming the Remove signal is selected to come from theIR 206, data will be shifted into the IR's Shift Register 304 during theShift-IR state 1210 of the Tap controller, then updated into the IR'sUpdate Register 306 in response to the UpdateIR control signal duringthe Update-IR state 1212 of the Tap controller. Since the Remove signal910 is output from the IR's Shift Register on bus 312 to DFF 1102, boththe IR's Update Register 306 and DFF 1102 will be updated in response tothe UpdateIR control signal at the same time. Thus changes in the outputof DFF 1102 (Remove Select) will occur synchronous to changes in theoutput bus 310 of IR Update Register 306. Similarly, if the Removesignal 910 is selected to come from the DR 208, this approach will causea change in the output of DFF 1102 to occur synchronous to changes inthe output bus 310 of the DR's Update Register 306. If the Remove signalwere to be input to DFF 1102 from the IR's or DR's Update Register bus310, it is clear that the change in the output of DFF 1102 could notoccur at the same time as the change in output bus 310 since bus 310 hasto change first to provide the Remove signal to the input of DFF 1102.While the circuit examples of the present disclosure are designed suchthat the changes in the outputs of DFF 1102 and Update Register 306occur synchronously, it should be clear that other example circuitscould be designed to support a non-synchronous change approach. Forexample, the clock input of DFF 1102 could be made falling edgetriggered to allow for receiving the Remove signal from the UpdateRegister 306 bus 310 on the rising edge of the UpdateIR or UpdateDRcontrol signal and clocking the Remove signal into the DFF 1102 on thefalling edge of the UpdateIR or UpdateDR control signal.

The decision as to whether the Remove signal 910 comes from the IR 206or the DR 208 of the TDS 920 Tap controller is by design choice. Oneadvantage of having the Remove signal come from the IR 206 instead offrom the DR 208 is that it allows Tap domain selection and TDS circuit920 removal operations to occur in a single step process, i.e. inresponse to only an IEEE 1149.1 instruction scan operation. If theRemove signal came from the DR 208, Tap domain selection and TDS circuitremoval operations would require a two step process, i.e. an IEEE 1149.1instruction scan to select the DR 208 followed by an IEEE 1149.1 datascan to load data into the selected DR to perform the Tap domainselection and TDS circuit removal operation.

From the above description it is clear that outputting the Remove signalfrom TDS 920 to multiplexer control circuit 906 using IEEE 1149.1instruction and data scan operations will cause the Remove Select 914signal to be set high. Once Remove Select 914 is set high, multiplexer904 couples serial path 118 to the IC's TDO output 912 and enables thefunction of the blocking circuit 1002 in the TDS's Tap controller. Thisbrings about the TDS removal aspect of the present disclosure andenables the TDI to TDO scan path configurations shown in FIGS. 6 and 8.It is clear that once the TDS 920 is removed from the TDI to TDO scanpath, conventional IEEE 1149.1 instruction and data scans cannot be usedto replace it back into the TDI to TDO scan path since access to theTDS's IR and DR are no longer available. The following descriptiondescribes the TDS replacement aspect of the present disclosure.

The replacement of TDS 920 back into the IC's TDI to TDO scan path isachieved by the previously mentioned special protocol, which is based ona non-conventional operation of the TMS and TCK signals of bus 124. Asseen in FIG. 11, if the Replace State and Reset signals of bus 908 arehigh, DFFs 1104 and 1106 may be clocked by the TMS 124 signal. In thiscondition, a clock pulse comprising a rising edge and a falling edge onTMS 124 will cause the low input of DFF 1104 to be clocked to theReplace output of DFF 1106. Clocking the Replace output of DFF 1106 to alow will clear DFF 1102, causing the Remove Select output 914 to be setlow. With Remove Select set low, multiplexer 904 selects TDS serialoutput 918 to be coupled to the IC's TDO output 912 and allows theblocking circuit 1002 to couple Tap control output bus 1004 to IR and DRcontrol input bus 1006. Thus after the special protocol is input on TMS124, the TDS 920 is again replaced in the ICs TDI to TDO scan path andmade available for access. This brings about the TDS replacement aspectof the present disclosure and enables the TDI to TDO scan pathconfigurations shown in FIGS. 5 and 7.

In FIG. 13, an example is shown of conventional operation of the TCK andTMS signals moving the Tap controller into and from Tap controllerstates Run/Test Idle 1204, Shift-IR 1210, Shift-DR 1214, Pause-IR 1208,and Pause-DR 1206. These states, as indicated in FIG. 12, are referredto as the Replace State. As previously mentioned, the Replace Statesignal on bus 908 is set high during the Replace State. Referring toboth FIGS. 12 and 13, it is seen that these states are entered byasserting a logic zero on TMS. After entering the states, the Tapcontroller will hold in these states if TMS remains a logic zero. Exitfrom the states is achieved by asserting a logic one on TMS. Thefunction of each of these Tap controller states is well known anddescribed in the IEEE 1149.1 standard.

FIG. 14 illustrates the application of the special protocol used toreplace the TDS circuit 920 back into the IC's TDI to TDO scan path torealize the configurations seen in FIGS. 5 and 7, with TDS 920substituted for TDS 104. As seen, the Replace State is conventionallyentered by asserting a logic low on TMS. In this example, the TMS signalis held low to cause a first Hold operation to occur in the ReplaceState. Following this first Hold operation the TCK is halted at a logiczero level. While TCK is halted, a clock pulse is input on TMS. This TMSclock pulse, as described above, sets the Replace output of DFF 1106 lowto enable and insert the TDS circuit back into the IC's TDI to TDO scanpath. Following the TMS clock pulse, the TCK is again made active toperform a second Hold operation. Following the second Hold operation,TMS is set high to cause an Exit from the Replace State on the next TCKclock.

In FIG. 15, an example is shown of conventional operation of the TCK andTMS signals moving the Tap controller into and from Tap controllerstates Run/Test Idle 1204, Shift-IR 1210, Shift-DR 1214, Pause-IR 1208,and Pause-DR 1206, again indicated as the Replace State. In thisexample, the Tap controller does not Hold in the Replace State as it didin FIGS. 13 and 14, but simply passes through it by setting TMS low toEnter the Replace State and then high to Exit the Replace State.

FIG. 16 illustrates the application of the special protocol used toreplace the TDS circuit 920 back into the IC's TDI to TDO scan path. Asseen, the Replace State is conventionally Entered by asserting a logiclow on TMS. After the Replace State is Entered, the TCK is halted at alogic zero level. While TCK is halted, a clock pulse is input on TMS.This TMS clock pulse, as described above, sets the Replace output of DFF1106 low to enable and insert the TDS circuit back into the IC's TDI toTDO scan path. Following the TMS clock pulse, TMS is set high then theTCK is made active to perform the Exit operation from the Replace State.

While the examples of FIGS. 14 and 16 show the TCK halted at logic zerolevel when the special protocol (clock pulse) is input on TMS, the TCKcould have been halted at a logic one level as well. Further, while thespecial protocol is described as a single clock pulse occurring on TMSduring the Replace State and while TCK is halted, the special protocolcould be multiple clock pulses occurring during the same conditions. Forexample, the simple DFF 1104 and DFF 1106 circuit arrangement inmultiplexer controller 906 could be replaced with a different circuitthat requires more that one TMS clock pulse to set the Replace outputsignal to And gate 1110 high. Thus while the special protocol of thepresent disclosure is described as requiring only one TMS clock pulse tooccur while in the Replace State with TCK halted, any number of TMSclock pulses may be produced during the same conditions. It is importantto note that the special protocol shown in FIGS. 14 and 16 is notrecognized by the Tap controller 204 of any Tap domain, since the TCK ishalted. Thus the special protocol can be used to replace TDS circuits920 back into an IC's TDI to TDO scan path without modifying the stateof any Tap Domain, i.e. the input of the special protocol is transparentto all conventional IEEE 1149.1 test circuitry coupled to the TMS andTCK signals 124. It is possible to not have to halt the TCK if the TMSclock pulse(s) can be applied during an appropriate point in time withina single TCK clock period.

In normal operation of the Tap controller, the TMS signal 124 may changestate once between first and second TCK inputs 124. For example, in FIG.15 the normal operation of the TMS signal is seen to change state atpoint 1502 in the timing diagram between the Enter TCK and the Exit TCKinputs, i.e. during the shaded Replace State time frame. Since this TMSstate change occurs in the Replace State (Replace State input to Andgate 1108 is high), DFF 1104 of FIG. 11 will be enabled to clock in thelow at its input. Since during normal operation a second TMS statechange does not occur, the low at the output of DFF 1104 is not allowedto be clocked into DFF 1106 to set the Replace signal low. When the Tapcontroller transitions, during the Exit TCK, to a state different fromthe Replace State, DFF 1104 will be set back high by the low input onthe Replace State signal to And gate 1108. Thus during Tap controlleroperation, the low at the input of DFF 1104 cannot be clocked to theoutput of DFF 1106. This prevents the special protocol from beingfalsely recognized during normal operation of the Tap controller.

The special protocol is designed to be recognized only when the TMSsignal changes state at least twice while the Tap controller is in theReplace State. Using the special protocol example shown in FIG. 16, itis seen that the first TMS state change occurs at point 1602 of thetiming diagram and the second TMS state change occurs at point 1604 ofthe timing diagram. DFF 1104 serves to detect the first TMS state changeat point 1602 to clock in the low at its input and DFF 1106 serves todetect the second TMS state change at point 1604 to clock the low inputfrom DFF 1104 to its Replace output. Thus the arrangement of DFFs 1104and 1106 are designed to only recognize the special protocol if and onlyif both TMS state transitions 1602 and 1604 occur between the Enter TCKand Exit TCK of FIG. 16. This insures the Replace signal output of DFF1106 can never be set low during normal operation of the TMS signal,which as mentioned above only changes state once between TCK inputs.

FIG. 17 is shown to simply indicate that circuit block 916 may exist atthe beginning (near TDI) of an IC's TDI to TDO scan path instead of atthe ending (near TDO) as seen in FIG. 9. If placed at the beginning ofan IC's TDI to TDO scan path, the IC's TDI input 1702 would be coupledto TDS circuit 920 and multiplexer circuit 904 of circuit block 916 inplace of the serial path output 118 of Tap domain circuit block 106 inFIG. 9. The output 1706 of multiplexer circuit 904 of circuit block 916would be coupled to the TDI input of Tap domain circuit block 106 inplace of the IC's TDI input of the example in FIG. 9. The serial pathoutput 118 of Tap domain block 106 would be coupled to the IC's TDOoutput 1704. The function of TDS 920 to select Tap domains in circuitblock 106 and to remove and replace itself in the IC's TDI to TDO scanpath is independent of its position in the IC's TDI to TDO scan path.

FIG. 18 illustrates use of circuit block 916 in an IC 1802 with a Tapdomain circuit block 1804 that contains two Tap domains TD1 and TD2 aspreviously described and a new circuit referred to as a Tap DomainBypass (TDB) circuit 1806. As seen, circuit block 916 is positioned nextto TDI, which as mentioned in regard to FIG. 17 does not effect itsoperation. This example is similar to the one in FIGS. 9 (and 17) inthat circuit block 916 can select any one or both of the two Tap domainsTD1 and TD2 in circuit block 1804 between the IC's TDI 1702 to TDO 1704leads. This example differs from the FIGS. 9 and 17 examples in that thenew TDB circuit 1806 can also be selected between the IC's TDI and TDOleads. Selecting the TDB circuit 1806 between the TDI and TDO leads andremoving TDS 920 provides a scan path through the IC that only includesa single scan register bit during both IEEE 1149.1 instruction and dataregister scan operations. Conventional IEEE 1149.1 Tap domainarchitectures have a bypass register bit that be selected to provide asingle scan register bit between an IC's TDI and TDO leads during dataregister scan operations. However during instruction scan operations,conventional IEEE 1149.1 Tap domain architectures always scan throughthe instruction register from TDI to TDO. The TDB circuit 1806 of FIG.18 provides an approach whereby all Tap domains in an IC are bypassedand scan operations occur through a single scan register bit between theIC's TDI and TDO leads during both data and instruction scan operations.

FIG. 19 illustrates an example TDB circuit 1806. The TDB circuitconsists of a DFF 1902, an Or gate 1904, and a Tap controller 204. Theinput to DFF 1902 is coupled to TDI 1906 which is input from the inputlinking circuit 108 of FIG. 18 as described for the Tap domains TD1-3 ofFIG. 1. The output of DFF 1902 is coupled to TDO 1908 which is output tothe output linking circuit 110 of FIG. 18 as described for the Tapdomains TD1-3 of FIG. 1. The clock input of DFF 1902 comes from theoutput of Or gate 1904. The inputs of Or gate 1904 are coupled to theClockDR and ClockIR outputs from Tap controller 204. The Tapcontroller's TMS, TCK, and TRST inputs 1910 come from the input linkingcircuit 108. When TDB 1806 is selected between TDI and TDO and its Tapcontroller 204 is in the Shift-DR 1214 state during data scanoperations, the ClockDR output will be active to pass through the Orgate to shift data through DFF 1902 from TDI 1906 to TDO 1908. When TDB1806 is selected and its Tap controller 204 is in the Shift-IR 1210state during instruction scan operations, the ClockIR output will beactive to pass through the Or gate to shift data through DFF 1902 fromTDI 1906 to TDO 1908. When TDB 1806 is selected between the TDI and TDOleads of IC 1802 and TDS 920 of circuit block 916 is removed, the Tapdomains TD 1-2 will be deselected and a single scan path register bit(DFF 1902) will exist between the IC's TDI and TDO leads during bothIEEE 1149.1 instruction and data scan operations.

FIG. 20 illustrates a scan path 2002 containing four ICs 1802. Each ICis shown with TDS 920 of circuit block 916 in the scan path and with oneTap domain's IR 206 and DR 208 in the scan path. With the exception ofTDS 920 of circuit block 916 being positioned near TDI thisconfiguration is similar to that shown in FIG. 5.

FIG. 21 illustrates the scan path 2002 of FIG. 20 after the first,second and fourth IC have had their TDB circuit 1806 selected and theirTDS 920 of circuit 916 removed from their scan paths. The third IC has aTap domain selected, TD1 or TD2, and has the TDS 920 removed from itsscan path. In this configuration, the scan paths of the first, second,and fourth ICs appear as single scan bits during IEEE 1149.1 instructionand data scan operations to the third IC. Data scan patterns to the DR208 of the third IC simply include leading and trailing pad bits tocompensate for the TDB circuits 1806 of the first, second and fourth IC.Likewise, instruction scan patterns to the IR 208 of the third IC simplyinclude the same leading and trailing pad bits to again compensate forthe TDB circuits 1806 of the first, second, and fourth IC. The TDBcircuits of the first, second, and fourth IC make the scan path 2002appear as if it contains only the Tap domain of the third IC. Thus theinstruction and data pattern set of the selected Tap domain of the thirdIC can be used directly once the pad bits have been added. After accessof the Tap domain of the third IC is complete, the TDS circuits 906 ofcircuit blocks 916 are replaced in the scan path 2002, using the specialprotocol, to allow selecting Tap domains of another IC or ICs andaccessing those Tap domains via TDB circuits 1806 in the other ICs.

FIG. 22 illustrates a scan path 2202 containing four ICs. The first,second and fourth ICs 1802 contain circuit blocks 916 and 1804. Thethird IC 704 is a legacy IC that only contains one Tap domain 202. Thepurpose of this example is to show that ICs including the TDB circuit1806 of the present disclosure may operate in a scan chain with legacyICs, like in FIG. 7. In FIG. 22 the first, second and fourth ICs 1802include one selected Tap domain's IR 206 and DR 208 and TDS 920 ofcircuit block 916 in the scan path.

FIG. 23 illustrates the scan path 2202 after the first, second, andfourth ICs have selected their TDB circuit 1806 and have removed theirTDS circuit 920. As can be seen, IEEE 1149.1 instruction and data scanoperations to the legacy IC 704 is simplified and streamlined due to thesingle scan register bit paths through the TDB circuits 1806 of thefirst, second, and fourth ICs.

FIG. 24 illustrates an IC that contains circuit block 2404 and circuitblock 916. Circuit block 2404 contains a single Tap domain 202, TDBcircuit 1806, input linking circuit 2406 and output linking circuit 110.Tap domain 202 is assumed to be the IEEE standard 1149.1 boundary scanTap domain. The input linking circuit 2406 differs from input linkingcircuit 108 in that it does not need TDI multiplexers since only one Tapdomain exists in the circuit, which allows the IC's TDI input to becoupled directly to the TDI inputs of Tap domain 202 and TDB circuit1806. The input linking circuitry 2406 only contains gating logic,controlled by bus 126, to selectively switch the IC's TMS and TCK inputs124 to the TMS and TCK input buses 2408 and 2410 of TDB circuit 1806 andTap domain 202, respectively. The IC's TRST input is always coupled tothe Tap domain 202 and TDB 1806. This example illustrates that the IEEE1149.1 boundary scan Tap domain may be augmented to include TDB circuit1806 and circuit block 916 to allow the IC to operate using either theIEEE 1149.1 Tap domain coupled between TDI 2412 and TDO 2414 or the TDBcircuit 1806 coupled between TDI and TDO. Thus ICs like that of FIG. 24would have a conventional IEEE 1149.1 mode of operation and the new modeof operation whereby the IC's TDI and TDO leads may be coupled togethervia a single scan register bit (DFF 1902) to simplify and streamlineinstruction and data scan operations to other ICs coupled to IC 2402 ina scan path.

Although the present disclosure has been described in detail, it shouldbe understood that various changes, substitutions and alterations may bemade without departing from the spirit and scope of the disclosure asdefined by the appended claims.

What is claimed is:
 1. An integrated circuit comprising: A. a TDI inputlead, a TDO output lead, a TCK input lead, and a TMS input lead; B.plural first TAP domains each having a TDI input coupled to the TDIinput lead, a TDO output selectively coupled to the TDO output lead, aTCK input coupled to the TCK input lead, and a TMS input selectivelycoupled to the TMS input lead; C. input linking circuitry coupled to theTDI input lead, the TCK input lead, and the TMS input lead and coupledto the TDI input, TCK input, and the TMS input of each TAP domain, theinput linking circuitry having control inputs; D. output linkingcircuitry coupled to the TDO output of each TAP domain and having a TDOoutput selectively coupled to the TDO output lead, the output linkingcircuitry having control inputs; and E. second TAP domain circuitryincluding: i. TAP domain selection circuitry, the TAP domain selectioncircuitry having a TCK input coupled to the TCK input lead, a TMS inputcoupled to the TMS input lead, a TDI input coupled to the TDI inputlead, a TDO output coupled to the TDO output lead, control output leadscoupled to the control inputs of the input linking circuitry and theoutput linking circuitry, and a remove select input; and ii. multiplexercontrol circuitry having a TMS input coupled to the TMS input lead and aremove select output coupled to the remove select input.
 2. Theintegrated circuit of claim 1 in which the TAP domain selectioncircuitry is coupled between the plural first TAP domains and the TDOoutput lead.
 3. The integrated circuit of claim 1 in which the TAPdomain selection circuitry is connected between the TDI input lead andthe plural first TAP domains.